Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1051

reference
689-tree-1
name
1051
tree-preservation-order

undefined

689-tpo-1
uprn
address-text
point
POINT (-1.017852 50.881915)
geometry
MULTIPOLYGON (((-1.017810 50.881911,-1.017812 50.881919,-1.017818 50.881927,-1.017827 50.881933,-1.017839 50.881937,-1.017852 50.881938,-1.017865 50.881937,-1.017877 50.881933,-1.017887 50.881927,-1.017893 50.881920,-1.017895 50.881911,-1.017893 50.881903,-1.017887 50.881895,-1.017878 50.881889,-1.017866 50.881885,-1.017853 50.881884,-1.017840 50.881885,-1.017828 50.881889,-1.017818 50.881895,-1.017812 50.881902,-1.017810 50.881911)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL